[Back]

Rhapsody Developer Release Copyright 1998 by Apple Computer, Inc. All Rights Reserved.

Rhapsody Developer Release Notes:
MallocDebug

This file contains release notes for the Developer Release of MallocDebug. MallocDebug is an application you can use to measure the dynamic memory usage of applications and to find memory leaks. MallocDebug can measure and analyze all allocated memory in an application and can measure the memory allocated since a given point in time. MallocDebug also contains a conservative garbage detector with which to detect memory leaks.

 

Notes Specific to Premier Release

New Features

Online help has been updated from the OpenStep version to reflect changes to the application.

 

Using MallocDebug

To measure your application's malloc() usage with MallocDebug, first choose Select from the File menu and select the application to run. The application starts up, and MallocDebug causes it to link dynamically against a special version of malloc() that enables debugging. Next select the application to monitor by choosing Open from the File menu; select an application in the Select panel by double-clicking its icon, and MallocDebug's application window will appear. For more information on using MallocDebug see the MallocDebug documentation (accessed through the Help menu).

 

Known Problems

The following new bugs have appeared since the OPENSTEP 4.2 release:

Reference

2200482

Releases

Rhapsody Developer

Problem

Find Previous command is buggy

Description

Sometimes choosing the Edit->Find->Previous command results in an error message displayed in the console:

[NSConcreteMutableArray objectAtIndex]: index (1) beyond bounds (1)

Reference

2203369

Releases

Rhapsody Developer

Problem

MallocDebug crashes when application being examined terminates

Description

MallocDebug crashes if you try to use the MallocDebug Interface with a process that has been terminated. For example, say you are using MallocDebug to examine your applications memory use, and you have the MallocDebug Interface open so that you can browse memory usage. You then quit your application and leave the MallocDebug interface to the application being open. If you then go back to the MallocDebug interface and try to do something else, such as examine leaks, MallocDebug will terminate.

Workaround

Do not use the MallocDebug interface after terminating the application being examined. Instead, close the MallocDebug interface to the application once the application being examined has quit.